Docs: clarify Tailwind CSS v4 PostCSS setup and upgrade notes for Lararvel #2207
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
|
Hey! Thanks for the contribution but I'm not sure if the installation guide is the right place for this. It seems like a new laravel app does not come with a In my mental model, the installation guides should be for new setups that have not used Tailwind CSS before, that's how all of the guides are written right now. I hope this makes sense! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Many developers — particularly those using Laravel — have faced confusion when upgrading to Tailwind CSS v4, as seen in issue #15735.
The main issue comes from legacy configuration in
postcss.config.jsthat still includestailwindcssas a plugin. This now causes an error in v4:Laravel’s default scaffolding has not yet been updated to reflect the Tailwind CSS v4 setup, which increases the likelihood of this issue occurring during fresh installs or upgrades.
This PR updates the installation section to clarify:
tailwindcss,postcss-import, andautoprefixershould be removed frompostcss.config.jsThis clarification should help prevent common setup errors and make the upgrade path smoother for developers working with Laravel or following older guides.